| Main Description |
The main result of a sprint is the partial product which implements, in addition to what was yet implmented at the
beginning of the sprint, additionnal requirements developed during this sprint.
3 usages can be made -after the demo during sprint review- out of the partial product obtained at the end of iteration:
-
it is not used outside of the team. It has been produced in order to minimize risks linked to technology and team's
capability to integrate to produce a
build . It usually happens at the beginning of a new product.
-
It is used by beta customers, in addition to the product owner. It allows them to play with it, which gives
feedback and reduces risks associated to UI and ergonomy. Feedbacks will feed the backlog for later consideration.
-
It is deployed or shipped and used by its end users. It's obviously what needs to be targeted since each version
brings up value. It's desirable to release it as soon as possible and available. But it is not generally possible
to deploy/ship at the end of each sprint: too much time would be spent to pass release tests on the whole system,
build and release on production environment, write user manuals, prepare and provide training to users... That is
why this particular work oftenly requires a preparation activity for deployment. But if one manages to perform all
these tasks in a limited time, deployment/shipping can be done more often than at the end of releases.
|
